Workflow Engine Diagram
Workflow Management Service components, dependencies, service exposure, persistent state handling, notification linkage, document linkage, and operational support technologies
⚙️
Workflow Consumers / CMS Services
SERVICE EXPOSURE LAYER
BFF
BFF / Orchestration
Submits workflow requests and queries workflow state for UI flows
API
Workflow API
Controlled entry point for create, update, approve, reject, assign, and query actions
QRY
Workflow Query API
Read models and search endpoints for tracked workflow items
Requests enter through controlled APIs, then flow into rule evaluation, state handling, and routing logic
WORKFLOW ENGINE CORE
Internal engine components responsible for lifecycle control and workflow execution
VAL
Request Validation
Validates payload, transition intent, required attributes, and submission readiness
AUTH
Authorization Check
Applies RBAC / ABAC and verifies the caller can perform the requested action
RULE
Workflow Rules Engine
Evaluates transitions, conditions, approval rules, and routing logic
STATE
State Manager
Creates and updates workflow instances and manages current lifecycle state
TASK
Task Router
Assigns actions, routes work items, and determines next responsible actor
APR
Approval Handler
Processes approve / reject / request-more-info paths and records decision events
ESC
Escalation Handler
Handles overdue, timed, or exception-based escalation scenarios
HIS
Comment / History Handler
Stores comments, change history, action trail, and state transition records
PERSISTENCE & INTEGRATION ADAPTERS
PERS
Persistence Adapter
Maps workflow state to the operational document store
DOC
Attachment Reference Handler
Links workflow items to files managed by the document service
NOT
Notification Integration
Triggers in-app and outbound notifications based on workflow events
AUD
Audit / Telemetry Adapter
Emits logs, metrics, traces, and audit events for observability
The workflow engine persists state, links attachments, notifies downstream services, and emits observability events
DEPENDENCIES & OPERATIONAL STORES
DDB
Azure DocumentDB
Stores workflow instances, current state, action history, routing metadata, and internal workflow-owned records
DOCS
Document Management Service
Provides controlled file upload / retrieval and attachment references for workflow-linked documents
NT
Notification Service
Creates internal notifications and can trigger outbound communication for workflow events
DD
Datadog
Receives logs, metrics, traces, and health signals from workflow processing paths
IDENTITY, CONTROL, AND DEPLOYMENT CONTEXT
AAD
Azure AD Context
Identity source for authenticated caller context reaching the workflow API
RBAC
RBAC / ABAC
Policy enforcement for permissions, attributes, and workflow action eligibility
DEP
Independent Deployability
The workflow engine is a separate service component with its own lifecycle and operational boundaries
EXPOSED OUTCOMES
CRT
Workflow Created
A tracked workflow instance is initialized
ASN
Request Assigned
Responsibility moves to next actor or queue
APR
Approved / Rejected
Decision outcomes are recorded and published
ESC
Escalated
Timeout or exception route is triggered
CMT
Comment / Attachment Linked
Supporting context is attached to the workflow record
Service exposure layer
Workflow engine core
Persistence & integration adapters
Dependencies & operational stores
Identity & deployability
Exposed workflow outcomes